When you select a Forced Master Copy for your Rule, SureSync will copy all the files from the source to the destination each and every time the job is run. This rule pays no attention to time and date stamps. If the source file is older, newer or equal it will still be copied to the destination. A Forced Master Copy does not delete files from the destination that are not present on the source.

Please note:

 

• Any changes made only to the destination files will be overwritten the next time the files are synchronized, so if there is a permanent change you want to make it must be made to the files on the source. There will be no warning.
• This is the only method that will copy files if the date stamps are the same.
• This method does not delete files. If you delete the source file manually, the destination file will be left as is at the next synchronization (it will not be deleted or replaced). If you delete a destination copy manually, the next time the files are synchronized a new copy will be synchronized from the source to the destination. If you want the ability to propagate deletes in a one-way rule, you must choose the mirror rule.

Possible Scenarios

Recovery from Damaged Files

A Forced Master Copy rule could be used if one of your machines has a virus or corrupted files. You can copy files from a clean machine to replace the damaged versions, and you would want SureSync to copy all files even if the modification dates are equal.

Testing SureSync

With a Forced Master Copy rule, you can simply run the same Relation over and over again to perform different tests. All of the data in the test root paths will be copied each time the job is run. This can make testing SureSync much simpler.

Summary Chart

The summary chart will give you a breakdown of how the Forced Master Copy rule functions when different events occur.